Repository navigation
chore: release v4.8.6 - #5109
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 11, 2026 11:24
c798009 to
c2ba28c
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 11, 2026 12:26
c2ba28c to
8dcdb5a
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 11, 2026 13:03
8dcdb5a to
438977c
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 11, 2026 13:58
438977c to
4b947cf
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
November 11, 2026 15:29
712829d to
56ad770
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 11, 2026 15:38
56ad770 to
9f298dc
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 11, 2026 16:16
9f298dc to
8cc2efd
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 11, 2026 17:20
8cc2efd to
78303ba
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 11, 2026 18:12
78303ba to
dd547b0
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 12, 2026 10:57
daaab13 to
ac01d64
Compare
matt-aitken
enabled auto-merge
November 12, 2026 13:31
matt-aitken
disabled auto-merge
November 12, 2026 13:37
Contributor
Author
🧭 Helm Chart Prerelease PublishedVersion: Install: helm upgrade --install trigger \
oci://ghcr.io/triggerdotdev/charts/trigger \
--version "4.8.6-pr5109.301388f"
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 12, 2026 14:04
ac01d64 to
301388f
Compare
0ski
approved these changes
Nov 12, 2026
ericallam
approved these changes
Nov 12, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 12, 2026
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 16, 2026 17:00
301388f to
90830c0
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 16, 2026 17:44
90830c0 to
10e18c5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 17, 2026 00:21
10e18c5 to
d71ca93
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 17, 2026 09:58
d71ca93 to
53e1c5f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 17, 2026 10:08
53e1c5f to
82c4f0e
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
11 new features, 19 improvements, 19 bug fixes.
Highlights
01337977e)Improvements
Deploys on the
bun-1.4runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster.import.meta.urland__dirnamestill point at your files under/app, so files you read next to your code must be in the image as before (e.g. withadditionalFiles). Setbuild.bunBytecode: falseintrigger.config.tsto turn compilation off. (8130e5e73)trigger devandtrigger deployno longer crash withspawn ... ENOENTon bun runtimes when Bun isn't installed at~/.bun. The CLI now falls back tobunon yourPATH(Homebrew, mise and similar installs), and if Bun still can't be started,trigger devreports a readable error andtrigger deployskips local skill discovery with a warning and carries on. (15797c9f2)Bundled task files now keep their project layout (for example
/app/src/trigger/tasks.mjs) when the CLI runs from outside the project, such asnpx trigger.dev deploy. Before, they could land under a path containing the project's location, away from the filesadditionalFilescopies next to them, so reads relative toimport.meta.urlfailed. (0c03b59b9)Show CLI command errors in the same error format as other CLI errors, and keep them visible with
--log-level error. (c515c3f74)Deploys now report a warmup command that loads your config and task files offline without running any task, so the platform can prepare faster run starts for your deployment. (
5479177af)Generate the machine ID and the managed run controller ID on first use instead of at import, so importing these modules draws no randomness and a process restored from a warm start does not reuse IDs drawn before it was saved. (
a8ac49cd3)Deploys on the
node-24andnode-26runtimes now build a Node compile cache for your bundled code during the image build, so runs spend less time compiling your tasks and their dependencies before they start.node-22deploys are unchanged. (cb1e7362f)Report a run whose process the kernel killed for running out of memory as
TASK_PROCESS_OOM_KILLED, rather than as a generic exit afterSIGKILL, when the out-of-memory kill is counted in the run's cgroup. (7a2a7dc80)Deployed task processes now receive secret environment variables only with the run, instead of also in the environment the process starts with. (
489a6dff3)Deployed task processes now start with the environment variables that Node, OpenSSL, libuv or the dynamic loader read only at startup (such as
LD_PRELOAD,OPENSSL_CONF,NODE_ICU_DATA,TZandUV_*), and the run's logs warn, by name only, about other startup-only variables (such asNODE_OPTIONS,MALLOC_*orGLIBC_TUNABLES) that arrive too late to take effect. (60d1774df)webhooks.notion()endpoints accept Notion's verification request. While the endpoint has no signing secret, theverification_tokenNotion sends is stored as its signing secret, so you can paste it back into Notion and later deliveries verify with it. Redeploy with this version for existing Notion endpoints to pick it up. (4288ea912)Support scoped run tokens without an environment key, including offloaded task inputs and stream waits. Explain why a run has no usable credential for an operation. (
ed0147895)Public-token helpers and chat token creation now prefer server minting for root API keys too, avoiding the legacy claims endpoint on compatible servers. Trigger, batch, and waitpoint responses missing a token also try server minting first. (
90d677b12)Root-key callers retain local-signing compatibility only when the mint endpoint is missing or an older server specifically rejects an empty scope list. Named API keys and run tokens never self-sign. Authorization failures, expiration validation errors, rate limits, and server or connection failures do not activate the fallback.
Server minting with a root key signs with that same authenticated key, including during its rotation grace period, rather than with its replacement. Tokens stop authenticating when that key's grace period ends or it is immediately revoked. Deploy this server update before upgrading the SDK if you rely on minting during root-key rotation; older servers can still reject grace-window keys.
Server-minted tokens use the API rate-limit budget and follow the server's expiration rules, including its 30-day maximum. Minting tokens without scopes requires self-hosted v4.8.4 or later unless the root-key compatibility fallback is available. The default expiration remains 15 minutes.
concurrencyKeynow also takes an object, so one run can be limited by two limits keyed by different things, like a cap per session and a cap per organization.defaultis the run's own key and every other entry gives a named limit its own key:concurrencyKey: { default: sessionId, [orgLimit.name]: orgId }. A string key works as before. (4961fc474)Bug fixes
child_process.fork()andspawn(process.execPath, ...)in compiledbun-1.4deploys. They started the run worker again instead of Bun, so the child never ran and the task hung.process.execPathnow points at the image'sbunbinary, as it does in uncompiled deploys. (d63b49ef3)webhooks.brex(), which now reads thewebhook-id,webhook-timestampandwebhook-signatureheaders Brex sends instead ofsvix-*headers, and forwebhooks.composio(), which now keys the signature with the secret's raw text as Composio does instead of base64-decoding it. PagerDuty, Sentry, Vercel, Zendesk, Attio, DocuSign and Intercom endpoints now default to pasting the provider-issued signing secret, and Linear and Calendly offer both generating and pasting one. Redeploy with this version for existing endpoints to pick up the change. (b5b311407)Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
dependabot/**.envfilter in the URL also acceptsdevelopment,stagingandproduction. The compare view has a copy button on each key, and each row's edit and delete buttons are named after the key and environment for screen readers.?aiHelp=,/ai-help) now prefill the chat composer instead of sending.TASK_RUN_DEQUEUED_MAX_RETRIESinstead of staying queued forever.RUN_ENGINE_STALE_COMPLETION_MODE=enforceon the webapp to switch it on.Raw changeset output
Releases
@trigger.dev/build@4.8.6
Patch Changes
@trigger.dev/core@4.8.6trigger.dev@4.8.6
Patch Changes
bun-1.4runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster.import.meta.urland__dirnamestill point at your files under/app, so files you read next to your code must be in the image as before (e.g. withadditionalFiles). Setbuild.bunBytecode: falseintrigger.config.tsto turn compilation off. (8130e5e73)child_process.fork()andspawn(process.execPath, ...)in compiledbun-1.4deploys. They started the run worker again instead of Bun, so the child never ran and the task hung.process.execPathnow points at the image'sbunbinary, as it does in uncompiled deploys. (d63b49ef3)trigger devandtrigger deployno longer crash withspawn ... ENOENTon bun runtimes when Bun isn't installed at~/.bun. The CLI now falls back tobunon yourPATH(Homebrew, mise and similar installs), and if Bun still can't be started,trigger devreports a readable error andtrigger deployskips local skill discovery with a warning and carries on. (15797c9f2)/app/src/trigger/tasks.mjs) when the CLI runs from outside the project, such asnpx trigger.dev deploy. Before, they could land under a path containing the project's location, away from the filesadditionalFilescopies next to them, so reads relative toimport.meta.urlfailed. (0c03b59b9)--log-level error. (c515c3f74)5479177af)a8ac49cd3)node-24andnode-26runtimes now build a Node compile cache for your bundled code during the image build, so runs spend less time compiling your tasks and their dependencies before they start.node-22deploys are unchanged. (cb1e7362f)TASK_PROCESS_OOM_KILLED, rather than as a generic exit afterSIGKILL, when the out-of-memory kill is counted in the run's cgroup. (7a2a7dc80)489a6dff3)LD_PRELOAD,OPENSSL_CONF,NODE_ICU_DATA,TZandUV_*), and the run's logs warn, by name only, about other startup-only variables (such asNODE_OPTIONS,MALLOC_*orGLIBC_TUNABLES) that arrive too late to take effect. (60d1774df)@trigger.dev/core@4.8.6@trigger.dev/build@4.8.6@trigger.dev/schema-to-json@4.8.6@trigger.dev/core@4.8.6
Patch Changes
Deploys on the
bun-1.4runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster.import.meta.urland__dirnamestill point at your files under/app, so files you read next to your code must be in the image as before (e.g. withadditionalFiles). Setbuild.bunBytecode: falseintrigger.config.tsto turn compilation off. (8130e5e73)trigger devandtrigger deployno longer crash withspawn ... ENOENTon bun runtimes when Bun isn't installed at~/.bun. The CLI now falls back tobunon yourPATH(Homebrew, mise and similar installs), and if Bun still can't be started,trigger devreports a readable error andtrigger deployskips local skill discovery with a warning and carries on. (15797c9f2)Deploys now report a warmup command that loads your config and task files offline without running any task, so the platform can prepare faster run starts for your deployment. (
5479177af)Allow an explicit audience when signing and verifying JWTs and user-actor tokens. (
01337977e)Generate the machine ID and the managed run controller ID on first use instead of at import, so importing these modules draws no randomness and a process restored from a warm start does not reuse IDs drawn before it was saved. (
a8ac49cd3)Deploys on the
node-24andnode-26runtimes now build a Node compile cache for your bundled code during the image build, so runs spend less time compiling your tasks and their dependencies before they start.node-22deploys are unchanged. (cb1e7362f)webhooks.notion()endpoints accept Notion's verification request. While the endpoint has no signing secret, theverification_tokenNotion sends is stored as its signing secret, so you can paste it back into Notion and later deliveries verify with it. Redeploy with this version for existing Notion endpoints to pick it up. (4288ea912)Support scoped run tokens without an environment key, including offloaded task inputs and stream waits. Explain why a run has no usable credential for an operation. (
ed0147895)Public-token helpers and chat token creation now prefer server minting for root API keys too, avoiding the legacy claims endpoint on compatible servers. Trigger, batch, and waitpoint responses missing a token also try server minting first. (
90d677b12)Root-key callers retain local-signing compatibility only when the mint endpoint is missing or an older server specifically rejects an empty scope list. Named API keys and run tokens never self-sign. Authorization failures, expiration validation errors, rate limits, and server or connection failures do not activate the fallback.
Server minting with a root key signs with that same authenticated key, including during its rotation grace period, rather than with its replacement. Tokens stop authenticating when that key's grace period ends or it is immediately revoked. Deploy this server update before upgrading the SDK if you rely on minting during root-key rotation; older servers can still reject grace-window keys.
Server-minted tokens use the API rate-limit budget and follow the server's expiration rules, including its 30-day maximum. Minting tokens without scopes requires self-hosted v4.8.4 or later unless the root-key compatibility fallback is available. The default expiration remains 15 minutes.
Fix webhook verification for
webhooks.brex(), which now reads thewebhook-id,webhook-timestampandwebhook-signatureheaders Brex sends instead ofsvix-*headers, and forwebhooks.composio(), which now keys the signature with the secret's raw text as Composio does instead of base64-decoding it. PagerDuty, Sentry, Vercel, Zendesk, Attio, DocuSign and Intercom endpoints now default to pasting the provider-issued signing secret, and Linear and Calendly offer both generating and pasting one. Redeploy with this version for existing endpoints to pick up the change. (b5b311407)@trigger.dev/linear@4.8.6
Patch Changes
@trigger.dev/core@4.8.6@trigger.dev/sdk@4.8.6@trigger.dev/python@4.8.6
Patch Changes
@trigger.dev/core@4.8.6@trigger.dev/sdk@4.8.6@trigger.dev/build@4.8.6@trigger.dev/react-hooks@4.8.6
Patch Changes
@trigger.dev/core@4.8.6@trigger.dev/redis-worker@4.8.6
Patch Changes
@trigger.dev/core@4.8.6@trigger.dev/rsc@4.8.6
Patch Changes
@trigger.dev/core@4.8.6@trigger.dev/schema-to-json@4.8.6
Patch Changes
@trigger.dev/core@4.8.6@trigger.dev/slack@4.8.6
Patch Changes
@trigger.dev/core@4.8.6@trigger.dev/sdk@4.8.6@trigger.dev/sdk@4.8.6
Patch Changes
concurrencyKeynow also takes an object, so one run can be limited by two limits keyed by different things, like a cap per session and a cap per organization.defaultis the run's own key and every other entry gives a named limit its own key:concurrencyKey: { default: sessionId, [orgLimit.name]: orgId }. A string key works as before. (4961fc474)webhooks.notion()endpoints accept Notion's verification request. While the endpoint has no signing secret, theverification_tokenNotion sends is stored as its signing secret, so you can paste it back into Notion and later deliveries verify with it. Redeploy with this version for existing Notion endpoints to pick it up. (4288ea912)Support scoped run tokens without an environment key, including offloaded task inputs and stream waits. Explain why a run has no usable credential for an operation. (
ed0147895)Public-token helpers and chat token creation now prefer server minting for root API keys too, avoiding the legacy claims endpoint on compatible servers. Trigger, batch, and waitpoint responses missing a token also try server minting first. (
90d677b12)Root-key callers retain local-signing compatibility only when the mint endpoint is missing or an older server specifically rejects an empty scope list. Named API keys and run tokens never self-sign. Authorization failures, expiration validation errors, rate limits, and server or connection failures do not activate the fallback.
Server minting with a root key signs with that same authenticated key, including during its rotation grace period, rather than with its replacement. Tokens stop authenticating when that key's grace period ends or it is immediately revoked. Deploy this server update before upgrading the SDK if you rely on minting during root-key rotation; older servers can still reject grace-window keys.
Server-minted tokens use the API rate-limit budget and follow the server's expiration rules, including its 30-day maximum. Minting tokens without scopes requires self-hosted v4.8.4 or later unless the root-key compatibility fallback is available. The default expiration remains 15 minutes.
Fix webhook verification for
webhooks.brex(), which now reads thewebhook-id,webhook-timestampandwebhook-signatureheaders Brex sends instead ofsvix-*headers, and forwebhooks.composio(), which now keys the signature with the secret's raw text as Composio does instead of base64-decoding it. PagerDuty, Sentry, Vercel, Zendesk, Attio, DocuSign and Intercom endpoints now default to pasting the provider-issued signing secret, and Linear and Calendly offer both generating and pasting one. Redeploy with this version for existing endpoints to pick up the change. (b5b311407)Updated dependencies:
@trigger.dev/core@4.8.6@trigger.dev/convex@4.8.6